2.5.138 Maintenance Release Notes

In This Topic...

Bug Fixes

  • Previously, in Bridge, the Assign Adjuster combo-box would not return any results for users signed in with an AdjusterSupervisor security role. As a result, users could not assign adjusters to a claim. This bug occurred because the Bridge service accounts used to retrieve adjusters in the webservice required elevated privilege in ICS. A fix has been implemented that provides ICS admin rights when updating a user if a user has the System Administrator role assigned to them in Bridge. This issue was found and fixed in version 2.5.138 of the Bridge Specialty suite.

  • Previously, a bug caused a validation error when creating a subsequent transaction for a policy term after creating a policy contraction. This problem occurred as a result of Bridge not allowing users to set the date of a subsequent transaction if the date fell outside the effective date. This validation error occurred when out of sequence Endorsements were set to false in the Master Cover - Policy Settings. A fix to the endorsement validation logic has been implemented that excludes all contractions and endorsements ending after the term valid until date. This issue was found in version 2.5.121 of the Bridge Specialty suite and has been fixed in version 2.5.121 and the latest.

  • Previously, unauthorized users could access documents exported from grids in the system. Now, security has been improved by restricting application access for those without an active user session.

  • Previously, an effective date calculation for an endorsement or adjusted policy term could result in a date calculation greater than the policy term. A code fix has been implemented so that when the effective date exceeds the policy term, the system sets the effective date equal to the expiry date.

  • Previously, if a Field or Grid code contained a period, Web APIs did not support mapping to top-level fields and grids. Now, a code change has been implemented that allows values to be mapped to top-level fields and grids with a period in the code. With this configuration, Field or Grid codes existing with only the difference of a period such as FieldA and Field.A will not work properly when using the API.

  • Previously, when a user tried to save a rate in the Master Cover - Rates screen, an error message could appear and a new row could be added in the grid. This error message appeared when users added a Premium Type in the grid and clicked Save. A code fix has been implemented that no longer adds a row if it generates an error message.

  • Previously, when the Agency Bill pay plan was selected for New Business policy, and the policy was canceled, an A/R receivable entry amount was miscalculated to be less than the sum of remaining New Business charges in the General Ledger accounts. Also, an additional General Ledger entry was created for Clearance account. A update to the code logic has been implemented to calculate the right A/R receivable entry amount to appear in the General Ledger entries, and additional General Ledger entries are no longer created for Clearance account.

  • Previously, a Field Evaluation Rule could be configured with fields not included in the workflow; as a result, the system crashed when a Field Evaluation Rule was called, and a server error message appeared. A bug fix has been implemented that indicates fields missing from the workflow, allowing users to identify incorrect Field Evaluation Rule configurations.

  • Previously, when importing charges from ClaimsXPress via web services, charges codes with "IND" and "EXP" were not processed and would not appear in the General Ledger Entry Report. Now, the web service has been extended to include the "IND" and "EXP" charge types.

  • Previously, when creating a cancellation transaction, clicking Save & Refresh would result in a server error. A bug fix has been implemented that saves and refreshes the screen when the user clicks Save & Refresh.